System and methods of installing and operating devices without explicit network addresses

ABSTRACT

A method of discovering addressing information of one or more upstream devices to respond to specific messages by a second device on behalf of the one or more upstream devices in a network includes acquiring the addressing information in an upstream direction from one or more downstream devices to the one or more upstream devices. The method further includes acquiring the addressing information in a downstream direction from the one or more upstream devices to the one or more downstream devices. The method further includes responding to specific messages using the acquired addressing information about the one or more upstream devices.

This application is a continuation of and claims priority to U.S. patent application Ser. No. 13/551,984, filed Jul. 18, 2012, now allowed, which is hereby incorporated by reference herein in its entirety.

This application incorporates by reference in their entireties the following applications, all of which have the same filing date as the present application: U.S. application Ser. No. 13/551,804, “Programmable Small Form-Factor Pluggable Module,” by Robitaille and Ostiguy, U.S. application Ser. No. 13/551,998 “Systems and Methods of Detecting and Assigning IP Addresses to Devices with ARP Requests,” by Robitaille and Lemieux, U.S. application Ser. No. 13/552,022, “Systems and Methods of Using Beacon Messages to Discover Devices Across Subnets,” by Robitaille and Bouffard, and U.S. application Ser. No. 13/552,063, “Systems and Methods of Discovering and Controlling Devices without Explicit Addressing,” by Robitaille and Bouffard.

TECHNICAL FIELD

This invention is directed towards addressing the need for installing and operating, without prior configuration or knowledge and without network addresses, devices in a network for handling service requests on behalf of other upstream or downstream devices.

BACKGROUND

Some devices in a network may not be able to perform Service Operations Administration and Maintenance (SOAM) and other functions on their own. Network operators are looking to deploy SOAM devices at different points inside their network infrastructure.

BRIEF SUMMARY

There is a need to install devices that can perform such SOAM and other functions on behalf of other upstream or downstream devices. These SOAM capable devices may or may not be permanently installed inside a network. By allowing their installation and operation without the need for an explicit network address, it is possible to reduce or eliminate the need for an explicit configuration resulting in easier and more efficient deployment and use of these devices. Since such devices are not assigned a network address, there is a need to be able to discover the devices in a network where it may not actively participate in the normal network protocols that are in use. With some networks, the IDs or labels used by the protocols are not necessarily the same in both directions. If the devices are not participating in the underlying protocols (ex. MPLS, L2TPv3, GTP-U, etc.), the devices may not readily know what ID or label to use to communicate.

The devices must also be able to be discovered without (but not excluding) being pre-programmed with information specific to the network or the control infrastructure.

One aspect of the present invention relates to a method of discovering addressing information of one or more upstream devices to respond to specific messages by a second device on behalf of the one or more upstream devices in a network. The method includes acquiring the addressing information in an upstream direction from one or more downstream devices to the one or more upstream devices. The method further includes acquiring the addressing information in a downstream direction from the one or more upstream devices to the one or more downstream devices. The method further includes responding to specific messages using the acquired addressing information about the one or more upstream devices.

Additional aspect of the present invention relates to a method of discovering addressing information of one or more upstream devices to respond to specific messages by a second device on behalf of the one or more upstream devices in a network. The method includes pre-programming the second device with test packets that include addressing information in an upstream direction for the one or more upstream devices in each test packet. The method additionally includes using upstream test packets for triggering one of the one or more upstream devices to respond with a packet including the addressing information in a downstream direction to one of one or more downstream devices from one of the one or more upstream devices. The method further includes responding to specific messages including requests for functions that the one or more upstream devices are unable to perform using the acquired addressing information about one of the one or more upstream devices.

An additional aspect of the present invention relates to a system of discovering addressing information of one or more upstream devices to respond to specific messages by a second device on behalf of the one or more upstream devices in a network. The system includes at least one downstream device coupled to a first processor; at least one upstream device coupled to a second processor; and a second device coupled to a third processor, the second device located between the at least one downstream device and the at least one upstream device. The second device is configured to acquire addressing information in an upstream direction from the at least one downstream device and in a downstream direction from the at least one upstream device in order for the second device to respond on behalf of the at least one upstream device to the specific messages including requests for functions that the one or more upstream devices are unable to perform.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other advantages of the present disclosure will become apparent upon reading the following detailed description and upon reference to the drawings.

FIG. 1 illustrates a Multiprotocol Label Switching Network(MPLS) network with an upstream device unable to perform SOAM functions, a device capable of performing SOAM functions on behalf of the upstream device and a downstream device capable of requesting SOAM functions;

FIG. 2 shows the flow of messages through a device that is capable of passively discovering labels or IDs for a network when it is not configured with any prior knowledge of other devices or of the network and is not assigned any unique addressing information inside that network;

FIG. 3 shows the flow of messages through a device that is capable of actively triggering the discovery of labels or IDs for a network when it is configured with some prior knowledge about other devices and is not assigned any unique addressing information inside that network;

FIG. 4 shows the flow of messages where a device handles SOAM functions using acquired information on behalf of an upstream device that is not capable of performing the requested SOAM functions.

While the invention is susceptible to various modifications and alternative forms, specific embodiments have been shown by way of example in the drawings and will be described in detail herein. It should be understood, however, that the invention is not intended to be limited to the particular forms disclosed. Rather, the invention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the invention as defined by the appended claims.

DETAILED DESCRIPTION

In order for a SOAM capable device to be inserted into a network and perform SOAM and other functions of behalf of an upstream device or a plurality of upstream devices unable to perform such SOAM functions, the device must be able to learn or acquire information about the addressing of the other devices for which it needs to perform the SOAM functions. This learning or acquiring shall be transparent to other devices in the network and must not interfere with normal operation of the network.

FIG. 1 illustrates a generic portion of a MPLS network. Downstream device 101 is a network device capable of requesting SOAM functions from other devices inside the network. The downstream device 101 may be a testing unit, a router or a remote node that is local or external to a subnet where a device 102 that is configured to perform SOAM functions is located. Device 104 is an upstream device inside the same network that is unable to perform SOAM functions. The upstream device 104 may be a router or a remote node that is local or external to a subnet where the device 102 is located. The device 102 is therefore inserted in front of the upstream device 104 in order to perform the SOAM functions on behalf of the upstream device 104. The device 102 incorporates a field programmable gate array (FPGA). According to another embodiment of the present invention, the device 102 incorporates an application specific integrated circuit (ASIC). The SOAM functions include monitoring traffic and diagnosing issues, performing remote in-service layer 1-4 loopback, ITU-T Y.1564, ITU-T Y.1731 and RFC 2544 performance testing and monitoring actual customer or user and network statistics via a management interface, and other functions.

In one embodiment, in order to learn, discover or acquire the required addressing information about the upstream device, the SOAM device may take a passive role. Referring now to FIG. 2, this can be achieved by inspecting particular messages sent to an upstream device 204 behind the device 202 using a tunneling protocol such as MPLS. The upstream device 204 could be for example a handset or an LTE EnodeB and needs to be in the tunnel of interest and capable to respond. Sometimes it is difficult to respond because of firewalls or lack of service for the message. One solution to this problem is to make sure that the device 202 is pre-programmed to passively look at any packets to and from the upstream device 204. Responses from the upstream device 204 are identified by using the IP address in the tunnel or in the label stack of packets originating from the upstream device 204. Other identifiers could also be used. The device 202 looks at the messages from the upstream device 204 and registers one or more labels or IDs that are useful.

In FIG. 2, the downstream device 201 sends a packet 205 with a frame 206 to the upstream device 204 which will require a response. The device 202 is in the tunnel of interest and inspects the packet 205, registering labels or IDs that are useful and then forwards the packet 205 with the frame 206 on to the upstream device 204. These labels and IDs may or may not have specific fields that are intended to aid in discovery of the addressing information of the upstream device 204. The upstream device 204 receives packet 205 with frame 206 and responds to the downstream device 201 with a packet 207 that contains a frame 208. The device 202 receives the packet 207 with the frame 208. The device 202 inspects the packet 207, registering labels and IDs that are useful and forwards the packet 207 on to the downstream device 201. The device 202 now has the required addressing information about the upstream device 204 to perform SOAM functions on behalf of the upstream device 204.

In another embodiment, in order to learn, discover or acquire the required addressing information about the upstream device, the SOAM device may take an active role. Referring now to FIG. 3, device 302 is pre-programmed with a first test message 306 aimed at triggering a response from an upstream device 304. According to one aspect of the present invention, the pre-programming includes providing, via configuration or other means, addressing information about the labels or IDs needed to address each of the upstream devices 304. The device 302 transmits a packet 306 with a frame 307 to the upstream device 304. The upstream device 304 receives the packet 306 with the frame 307. The upstream device 304 either has special software for the explicit purpose to handle the special packet 306 or the packet 306 is addressed to a service known as already active on upstream device 304. The upstream device 304 then responds to the device 302 with a packet 308 with a frame 309. The device 302 analyzes the packet 308 and registers one or more labels or IDs, and then discards the packet 308 (without forwarding it) to avoid disrupting the operation of the network. The device 302 now has the required addressing information about the upstream device 304 to perform SOAM functions on behalf of the upstream device 304.

Once the SOAM device has obtained the required addressing information about the upstream device as per the method illustrated by FIG. 2 or 3, it may begin to provide SOAM and other functions on behalf of the upstream device while letting other traffic flow transparently to and from the upstream device. Referring now to FIG. 4, a protocol flow diagram illustrates how downstream device 401 can request a SOAM function from upstream device 404 and how it is transparently handled by device 402.

The downstream device 401 transmits a SOAM packet 409 to device 402. The device 402 receives the packet 409. The device 402 determines whether the packet 409 is for a SOAM function that the device 402 needs to handle on behalf of an upstream device 404. If the packet 409 is for a SOAM function, the device 402 performs the requested SOAM function using the addressing information collected for the upstream device 404 and prepares a valid response packet 410. The response packet 410 is then received by the downstream device 401 and is handled as the response to the SOAM request in packet 409.

In another embodiment, it should be noted that the SOAM capable device may handle the SOAM function on behalf of a plurality of devices located upstream or downstream from the SOAM capable device. When providing SOAM functions on behalf of a plurality of other devices, the SOAM capable device will learn and store the labels or IDs for each flow direction for each of the learned devices.

The device to discover and the discoverer node are each coupled to a processor. The present invention includes systems having processors to provide various functionality to process information, and to determine results based on inputs. Generally, the processing may be achieved with a combination of hardware and software elements. The hardware aspects may include combinations of operatively coupled hardware components including microprocessors, logical circuitry, communication/networking ports, digital filters, memory, or logical circuitry. The processors may be adapted to perform operations specified by a computer-executable code, which may be stored on a computer readable medium.

The steps of the methods described herein may be achieved via an appropriate programmable processing device, such as an external conventional computer or an on-board field programmable gate array (FPGA) or digital signal processor (DSP), that executes software, or stored instructions. In general, physical processors and/or machines employed by embodiments of the present invention for any processing or evaluation may include one or more networked or non-networked general purpose computer systems, microprocessors, field programmable gate arrays (FPGA's), digital signal processors (DSP's), micro-controllers, and the like, programmed according to the teachings of the exemplary embodiments of the present invention, as is appreciated by those skilled in the computer and software arts. Appropriate software can be readily prepared by programmers of ordinary skill based on the teachings of the exemplary embodiments, as is appreciated by those skilled in the software arts. In addition, the devices and subsystems of the exemplary embodiments can be implemented by the preparation of application-specific integrated circuits or by interconnecting an appropriate network of conventional component circuits, as is appreciated by those skilled in the electrical arts. Thus, the exemplary embodiments are not limited to any specific combination of hardware circuitry and/or software.

Stored on any one or on a combination of computer readable media, the exemplary embodiments of the present invention may include software for controlling the devices and subsystems of the exemplary embodiments, for driving the devices and subsystems of the exemplary embodiments, for processing data and signals, for enabling the devices and subsystems of the exemplary embodiments to interact with a human user, and the like. Such software can include, but is not limited to, device drivers, firmware, operating systems, development tools, applications software, and the like. Such computer readable media further can include the computer program product of an embodiment of the present invention for performing all or a portion (if processing is distributed) of the processing performed in implementations. Computer code devices of the exemplary embodiments of the present invention can include any suitable interpretable or executable code mechanism, including but not limited to scripts, interpretable programs, dynamic link libraries (DLLs), Java classes and applets, complete executable programs, and the like. Moreover, parts of the processing of the exemplary embodiments of the present invention can be distributed for better performance, reliability, cost, and the like.

Common forms of computer-readable media may include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other suitable magnetic medium, a CD-ROM, CDRW, DVD, any other suitable optical medium, punch cards, paper tape, optical mark sheets, any other suitable physical medium with patterns of holes or other optically recognizable indicia, a RAM, a PROM, an EPROM, a FLASH-EPROM, any other suitable memory chip or cartridge, a carrier wave or any other suitable medium from which a computer can read.

While particular implementations and applications of the present disclosure have been illustrated and described, it is to be understood that the present disclosure is not limited to the precise construction and compositions disclosed herein and that various modifications, changes, and variations can be apparent from the foregoing descriptions without departing from the spirit and scope of the invention as defined in the appended claims. 

What is claimed is:
 1. A method of discovering addressing information of one or more first devices to respond to specific messages by a second device on behalf of the one or more first devices in a network, the method comprising: acquiring, by a second device not having a network address, addressing information in an upstream direction from one or more third devices to the one or more first devices; acquiring, by the second device, addressing information in a downstream direction from the one or more first devices to the one or more third devices; and responding, by the second device on behalf of the one or more first devices, to specific messages that include requests for functions that the one or more first devices are unable to perform.
 2. A method of discovering addressing information of one or more first devices to respond to specific messages by a second device on behalf of the one or more first devices in a network, the method comprising: pre-programming a second device with test packets that include addressing information in an upstream direction for the one or more first devices in each test packet; using upstream test packets for triggering one of the one or more first devices to respond with a packet including the addressing information in a downstream direction to one of one or more third devices from one of the one or more first devices; and responding to specific messages including requests for functions that the one or more first devices are unable to perform using the included addressing information about one of the one or more first devices.
 3. A system of discovering addressing information of one or more first devices to respond to specific messages by a second device on behalf of the one or more first devices-in a network, the system comprising: at least one third device coupled to a first processor; at least one first device coupled to a second processor; and a second device coupled to a third processor, the second device located between the at least one third device and the at least one first device, wherein the second device is configured to acquire addressing information in an upstream direction from the at least one third device and in a downstream direction from the at least one first device in order for the second device to respond on behalf of the at least one first device to the specific messages including requests for functions that the at least one first device is unable to perform.
 4. The method of claim 1, wherein the acquiring of the addressing information in the upstream direction includes: transmitting, by one of the one or more third devices, a packet with a frame to one of the one or more upstream devices; receiving, by the second device, the packet with the frame; inspecting, by the second device, the packet with the frame; storing, by the second device, labels, IDs and/or other useful information for one of the one or more first devices in the upstream direction; transmitting, by the second device, the packet with the frame to one of the one or more first devices; and receiving, by one of the one or more first devices, the packet with the frame.
 5. The method of claim 1, wherein the acquiring of the addressing information in the downstream direction includes: transmitting, by one of the one or more first devices, a packet with a frame, to one of the one or more third devices; receiving, by the second device, the packet with the frame; inspecting, by the second device, the packet with the frame; storing, by the second device, labels, IDs and/or other relevant information for one of the one or more first devices in the downstream direction; transmitting, by the second device, the packet with the frame, to one of the one or more third devices; and receiving, by one of the one or more third devices, the packet with the frame.
 6. The method of claim 1, wherein one of the one or more third devices is a testing unit, a router or a remote node that is local or external to a subnet where the second device is located.
 7. The method of claim 1, wherein one of the one or more first devices is a router or a remote node that is local or external to a subnet where the second device is located.
 8. The method of claim 1, wherein the second device incorporates a field programmable gate array (FPGA).
 9. The method of claim 1, wherein the second device incorporates an application specific integrated circuit (ASIC).
 10. The method of claim 1, wherein the second device is in a tunnel of interest.
 11. The method of claim 2, wherein the pre-programming the second device with test packets that includes addressing information in the upstream direction for the one or more first devices comprises: providing via configuration or other means, addressing information about labels or IDs needed to address each of the one or more first devices from the second device.
 12. The method of claim 2, wherein the acquiring of the addressing information in the downstream direction includes: transmitting, by the second device, a first packet with a first frame to a first device using a pre-programmed test packet, receiving, by one of the one or more first device, the first packet with the first frame, transmitting, by one of the one or more first devices, a second packet with a second frame, to one of the one or more third devices, receiving, by the second device, the second packet with the second frame, inspecting, by the second device, the second packet with the second frame, storing, by the second device, labels, IDs and/or other useful information for one of the one or more first device in the downstream direction, discarding the second packet from the second device.
 13. The method of claim 2, wherein responding to specific messages using the acquired addressing information about the one or more first devices comprises: transmitting, by one of the one or more third devices, a Service Operations Administration and Maintenance (SOAM) packet to the second device acting on behalf of one of the one or more first devices; receiving, by the second device, the SOAM packet including a SOAM function to be performed by the second device; inspecting, by the second device, the SOAM packet; performing, by the second device, the SOAM function requested in the packet; transmitting, by the second device, to one of the one or more third devices, a SOAM response packet using the addressing information about one of the one or more first devices previously gathered by the second device during inspection; and receiving, by one of the one or more third devices, a valid SOAM response in the packet.
 14. The method of claim 13, wherein the SOAM function includes monitoring network traffic and diagnosing issues, performing remote in-service layer 1-4 loopback, performance testing and monitoring actual customer and network statistics via a management interface.
 15. The method of claim 2, wherein one of the one or more third devices is a testing unit, a router or a remote node that is local or external to a subnet where the second device is located.
 16. The method of claim 2, wherein one of the one or more first devices is a router or a remote node that is local or external to a subnet where the second device is located.
 17. The method of claim 2, wherein the second device incorporates a field programmable gate array (FPGA).
 18. The method of claim 2, wherein the second device incorporates an application specific integrated circuit (ASIC).
 19. The method of claim 2, wherein the second device is in a tunnel of interest.
 20. The system of claim 3, wherein acquiring of the addressing information in the upstream direction includes: transmitting, by the at least one third device, a packet with a frame to the at least one first device; receiving, by the second device, the packet with the frame; inspecting, by the second device, the packet with the frame; storing, by the second device, labels, IDs and/or other useful information for the at least one first device in the upstream direction; transmitting, by the second device, the packet with the frame to the at least one first device; and receiving, by the at least one first device, the packet with the frame.
 21. The system of claim 3, wherein the acquiring of the addressing information in the downstream direction includes: transmitting, by the at least one first device, a packet with a frame, to the at least one third device; receiving, by the second device, the packet with the frame; inspecting, by the second device, the packet with the frame; storing, by the second device, labels, IDs and/or other relevant information for the at least one first device in the downstream direction; transmitting, by the second device, the packet with the frame, to the at least one third device; and receiving, by the at least one third device, the packet with the frame.
 22. The system of claim 3, wherein responding to specific messages using the acquired addressing information about first devices includes: transmitting, by the at least one third device, a Service Operations Administration and Maintenance (SOAM) packet to the second device acting on behalf of the at least one first device; receiving, by the second device, the SOAM packet including a SOAM function to be performed by the second device; inspecting, by the second device, the SOAM packet; performing, by the second device, the SOAM function requested in the packet, transmitting, by the second device, to the at least one third device, a SOAM response packet using the addressing information about the at least one first device previously gathered by the second device during inspection; and receiving, by the at least one third device, a valid SOAM response in the packet.
 23. The system of claim 22, wherein the SOAM function includes monitoring network traffic and diagnosing issues, performing remote in-service layer 1-4 loopback, performance testing or monitoring actual customer and network statistics via a management interface. 